We will also need to remove docs on VM_NO_TELEMETRY cc @nrichers

We will also need to remove docs on VM_NO_TELEMETRY cc @nrichers

@nibalizer the docs are generated off the codebase, so this should not require anything else.

PR Summary

This PR makes several changes, primarily focusing on removing Sentry telemetry and modifying dependency definitions. The key changes include:

1. Removal of Sentry-related functionality:

   • The API client (validmind/api_client.py) now no longer initializes Sentry telemetry. The helper functions related to Sentry (init_sentry and send_single_error) have been removed from validmind/logging.py.
   • The dependency on Sentry SDK has been modified in the lock file (sentry-sdk is now optional and tied to a specific extra marker) and removed as a direct dependency from pyproject.toml.

2. Updates to dependency metadata in the poetry.lock file:

   • A new entry for the package "presidio-structured" has been introduced with version 0.0.4a0 along with dependency settings and platform markers.
   • The marker for the existing "presidio-structured" version 0.0.6 has been updated to target Python versions >=3.11 appropriately for the pii-detection extra.
   • Adjustments to the spacy package entries, including a redefinition of markers for pii-detection, have been made. Several obsolete spacy entries (with older versions and their associated file lists) have been removed and a new version (3.8.7) is now included.

Overall, the changes streamline error logging by removing Sentry integrations and update dependency definitions to better align with supported Python versions and feature flags.

Test Suggestions

• Verify that API client operations (e.g., _ping and reload) function correctly without Sentry initialization, and that exceptions are raised as expected.
• Run integration tests to ensure that dependency resolution and package markers correctly select the intended version of packages (e.g., presidio-structured and spacy) based on the Python version and extras.
• Check that logging behavior remains robust and that error messages are being logged locally without attempting to send telemetry.
• Perform regression tests to ensure that the removal of Sentry functionality does not affect other parts of the system that rely on error logging.